This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Subject: HTTP Server: Waiting for session to finish - Description/Solution (In all probability a bug in domino 8 ?(http task))
Feedback Type: Problem
Product Area: Domino Server
Technical Area: Crash
Platform: Windows 2003 server
Release: 8.0.2
Reproducible: -Reproducibility-
After the domino updates from 7 to 8 we have recurring errors to the http task. On misc servers with different mail-dbs.
The http server stops responding.
Description.
There is no error message, no crash-info. The cpu usage increases to the http task.
When Console -> "tell http restart" the task does not restart. Then a error message is shown:
HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [3964] Thread ID [4164 (0x1044)] GET /path/database.nsf/formname?readform HTTP/1.1
Domino can not kill this state. We have to kill the hanging threads with a process explorer or to restart domino and windows.
In some cases a fixup on the related nsf releases the sessions without a restart.
We spent very much time in analyzing and found this:
When in a form a WebQueryOpen triggered agent opens a view/folder and this view/folder needs a rebuild of the index the browser waits and nothing happens. Now, when the user closes the browser window the thread is not destroyed and goes in close-wait state on the server (to see on OS Level). This means the "waiting for sessions" message when a "restart http" is done.
Right now the http task is instable/faulty and many other sessions/threads will go in close-wait status too. Later all resources are busy and the http server stops responding.
In this case we had mail-dbs which inboxes were working strange (in Notes the refresh-button appeared always and the inbox; the index was refreshed whenever it was opened). Deleting the inbox and Design refresh solved this problem.
When this folder is accessed from the browser directly (not via webQueryOpen triggered agent) the browser waits. A closed browser does not create a close_wait session. All is ok.
This is handled correctly from the domino server.
Workaround:
There is to do a view refresh before reading the view with such an WebQueryOpen triggered agent.
Solution:
With Version 7 we did not have this problem.
It is not addressed in version 8.0.2
In my mind this is a domino version 8 bug which is to fix (perhaps IBM / Lotus can give an answer?)
Feedback number WEBB7JJDJJ created by ~Emile Fezresatherflar on 09/16/2008